<?php
/**
 * <https://y.st./>
 * Copyright © 2016 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => "Should I switch from $a[Tor] to $a[I2P]?",
	'body' => <<<END
<p>
	I&apos;m thinking about switching to $[I2P].
	At the very least, I might switch to using $a[I2P] on the mobile.
	There are several factors to consider though.
	$a[I2P] addresses are less reliable than onion addresses, but they&apos;re also less centralized.
	That comparison needs to be explained a bit though.
	The second level domains under &quot;onion.&quot; in onion addresses are sixteen random characters long.
	$a[I2P] has a similar naming scheme, where the third level domains under &quot;b32.i2p.&quot; are fifty-two random characters long.
	The &quot;random&quot; characters in both cases are based on the hashes of the public keys, ans as a result, both ate pretty reliable, as total hash collisions aren&apos;t common.
	You could even say that $a[I2P] base 32 addresses are <strong>*more*</strong> reliable than onion addresses due to the fact that they&apos;re longer, so hash collisions are harder to create.
	However, almost no one uses these long, unreadable addresses, as far as I know.
	Instead, they use an address book that acts as a sort of hosts file.
	This allows the creation of very short, very meaningful names, like in regular $a[DNS].
	However, these names are as meaningless as domains listed in your system&apos;s <a href="file:///etc/hosts">hosts file</a>.
	While $a[I2P] address books are sharable across the network, one simple fact remains.
	The same host name could (and often probably does) exist in several different address books and point to very different places.
	There&apos;s no authoritative way to determine which one is the canonically-correct entry, and in fact, they basically are all equally correct.
	Names are very important for locating resources, so this seems like a huge problem to me.
	However, there&apos;s another way of looking at that issue as well.
	Onion addresses are defined by hidden service directories that $a[Tor] hidden services have to register with, and which other $a[Tor] clients have to use to perform lookups.
	The centralization of $a[Tor] gives the $a[Tor] Project a monopoly on that power; similar to the monopoly imposed by nonfree images such as those Orbot icons.
	$a[I2P] seems to lack those issues as far as I can see.
	$a[I2P] on mobile also lacks options for transparently proxying applications though, which is needed for applications that don&apos;t have proxy settings.
	$a[I2P] isn&apos;t as good for outproxying, either.
	I&apos;m told $a[I2P] uses $a[Tor] for outproxying, which means that instead of being able to use $a[I2P] to escape $a[Tor], I&apos;d be using $a[I2P] as another layer <strong>*in addition*</strong> to $a[Tor].
	Perhaps that&apos;s enough though.
	Debian protects me from whatever nonfree things the $a[Tor] project decides to throw in, at least in the main Debian packages, because of their strict licensing policies.
	Furthermore, $a[Tor] works just fine on the command line in Debian, so there are no images to get in the way.
	On the mobile though, graphical applications are needed and F-Droid doesn&apos;t provide the protections that it should against nonfree &quot;non-software&quot; parts of applications.
	The $a[I2P] layer would keep my mobile free while still connecting me to the main $a[Tor] network.
	I could continue using $a[Tor] directly on my laptop and server.
	Lastly, the &quot;i2p.&quot; pseudo$a[TLD] isn&apos;t recognized by $a[IANA], while the &quot;onion.&quot; special-use domain is.
	Then again, I&apos;m not really a fan of the way $a[IANA] operates.
	Should I even be bothered if I&apos;m using something that deviates from $a[IANA]&apos;s noxious standards? After all, they&apos;re the ones that demand that all domain registrants be available to be contacted via a telephone number.
</p>
<p>
	My project for the day was unpacking scattered bags of food into the cupboards.
	After that, I went and collected bullet shells in the forest with my mother.
</p>
END
);
